Configurable flux-system namespace #508
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the capability to set a different namespace for the Flux system than
flux-systemImportant for platform users, like Cozystack, where the system components are all expected to conform to a standard for namespaces eg
cozy-fluxcdI have this working locally, I'm only really interested in developing for the 0.26 branch so I've created
release-0.26If others are interested I will push this out as a release to the edge branch. However, be forewarned there are rough edges, as explained in #503 there is no support for current versions of VSCode. You have to be running an older version from October 2023, (this is surely dangerous, so YMMV and take care if you are still using this extension.)
I don't know how to do more releases on the 0.26 series now that 0.27 has started, the release machinery is quite involved.
0.27 will probably stay un-developed, it is missing lots of enhancements, please follow 0.26 if you are interested in this extension, but development has slowed or stopped, so we need interested contributors to let us know if they care to see this extension developed more in the future. Otherwise, I will keep it maintained only for my own use, as there are some bad compromises we made and I'm not prepared to unpack and undo them without an audience of any kind (might just leave it)