This message was deleted.
# infisical-feedback
s
This message was deleted.
s
is there already a way to do that @Tony @Maidul Islam @Vlad (Infisical)?
The use case for this is that developers in my team, for example, would work on different stages of a release cycle at the same time. Some of them are working to resolve issues from the current production build, some of them are working on fixes for current QA, and some of them are working on new features in the development phase
The way I view test, staging, and production here is more so for deployed instances in the different stages of the release (since we host these to facilitate user testing across the environments)
we're using gitflow by the way
v
yeah, I think it might be beneficial to copy/inherit environments (or maybe even create purely personal ones)
🚀 1
s
I imagine this to be something like
infisical pull
or something 🤣
or like scoping the tokens to a specific commit so that loading the secrets will always yield to the same set of secret values regardless if the actual value was updated by someone else
Feel free to share your thoughts ^
t
@Sheen Santos Capadngan I think this would depend on how many teams find this default behavior useful, currently one of the selling points is that you’ll always get the latest set of secrets at all times. Personally, I see the default behavior of getting the latest set of secrets as serving vast majority of use-cases. I’d think that what we can do instead is keep it as the default behavior and provide the option for teams to fetch secrets corresponding to a specific snapshot/commit if they choose to pass that in as a parameter whether it be via CLI or SDK — This I think is actually a very neat idea, I like it a lot. It’s like maybe you don’t have to rollback to a specific version, creating a commit on top of the latest one; instead you can just inject and specify a past commit. Is that what you have in mind?
🤘 1
s
Yeah that's exactly what i'm thinking @Tony
I feel like teams using the gitflow strategy would really benefit from this one but I agree
We can allow them to do this, but not by default
t
Cool cool. So maybe it’s like a flag on the CLI similar to
--env
?
👍 1
So maybe like
infisical run --env=dev --commit-1 -- npm start
👍 2
Commits should probably be referenced by
id
or something; numbered isn’t the way to go. Should generate a hash of sorts similar to git
s
agree ^
I have an ongoing initiative that I think would have to be a prerequisite for this one though, I'll tag you there
The above is my proposal to scope snapshots to specific environments
❤️ 1
v
Yeah @Akhi was actually working on this
s
oh wait really? can you fill me in with what's already being done?
v
Yeah, I think it’s best if @Akhi explains it 👌
🙏 1
m
Yes, this is being done as apart of our new feature: folders (you can store secrets within folders)
❤️ 1
🤣
v
Oh I think he’s talking about rolling back to specific environments
but it will be even better, because you will be able to rollback any folder
s
that's nice!
I'm okay with working on this one by the way @Tony @Vlad (Infisical). I'll just wait on @Akhi to finish with the folders feature
Curious, where can I find which task you guys are working on so that I can coordinate accordingly? Just so we don't work on the same thing 🤣
t
Sounds good!
Umm @Sheen Santos Capadngan you might find some ongoing task updates in the roadmap; doing my best to keep it updated time to time. I’m personally this week working on ongoing SOC 2 certification activities 😄
🚀 1
👍 1