Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use hash of the cluster stack instead of git commit hash #45

Open
aniruddha2000 opened this issue Jan 26, 2024 · 0 comments
Open

Use hash of the cluster stack instead of git commit hash #45

aniruddha2000 opened this issue Jan 26, 2024 · 0 comments
Assignees
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling

Comments

@aniruddha2000
Copy link
Member

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Independence from Git: This means csmctl can be used in a regular directory without a git repository, enhancing its versatility.

Immediate hash updates with changes in the cluster stack: This would eliminate the need for committing changes to get a new hash. It reduces the risk of errors, such as forgetting to commit changes, which can lead to significant delays

The only potential downside might be the loss of a one-to-one relationship between the commit hash and the cluster-stack hash in the CI process. However, I can't foresee a scenario where this would be a significant issue.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • csmctl version: (use kubectl version)
@aniruddha2000 aniruddha2000 self-assigned this Jan 26, 2024
@janiskemper janiskemper added the Container Issues or pull requests relevant for Team 2: Container Infra and Tooling label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling
Projects
Status: Backlog
Development

No branches or pull requests

2 participants