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

feat: Add labels to deployed dynamic objects #134

Merged
merged 10 commits into from
Jan 16, 2024
Merged

feat: Add labels to deployed dynamic objects #134

merged 10 commits into from
Jan 16, 2024

Conversation

Techassi
Copy link
Member

@Techassi Techassi commented Oct 30, 2023

Tracked by #148, part of stackabletech/issues#188

This adds labels to all deployed DynamicObjects. The implementation is a little messy and requires some internal restructuring to accommodate future changes. Code should be split into more sub-crates. A high-level overview might look something like this:

stackablectl -> client -> common business logic -> renderer -> output

Adds /demos and /stacks folder to gitignore. These folders can be
used to create local-only demo and stack tests. It also removed the
(accidentally) published demo files.
@Techassi Techassi marked this pull request as ready for review January 15, 2024 14:40
@Techassi
Copy link
Member Author

TODO: Remove any unwraps, final code clean-up.

@Techassi Techassi changed the title feat: Add labels to deployed resources feat: Add labels to deployed dynamic objects Jan 16, 2024
Copy link
Contributor

@fhennig fhennig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice work

@Techassi Techassi added this pull request to the merge queue Jan 16, 2024
Merged via the queue into main with commit 645a115 Jan 16, 2024
40 checks passed
@Techassi Techassi deleted the feat/labels branch January 16, 2024 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants