You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are your plans for supporting additional features on the Stack/compose file level that manipulate the file in a way that makes it easier to use but change the contract?
What I had in mind, would be addint functionality to this project that mirrors what we are doing in docker-sdp - we hash the config/secret file and append a hash to it so that rotation of configs/secrets works seamlessly (you still have to clean up the old secrets/configs, though).
The text was updated successfully, but these errors were encountered:
Ive not considered adding other features so far. The sole purpose up to this point has been to create a cli tool with docker stack deploy's cli api that is compliant with compose spec. That is not to say that I wouldn't consider adding something like you mentioned, I am just unaware of so many use cases and hadn't considered that direction.
First of all: This is an awesome effort.
What are your plans for supporting additional features on the Stack/compose file level that manipulate the file in a way that makes it easier to use but change the contract?
What I had in mind, would be addint functionality to this project that mirrors what we are doing in docker-sdp - we hash the config/secret file and append a hash to it so that rotation of configs/secrets works seamlessly (you still have to clean up the old secrets/configs, though).
The text was updated successfully, but these errors were encountered: