Autocomplete dropdown for secret referencing

[rohan-chaturvedi]

Is your feature request related to a problem?

Secrets can be created with references to other secrets in the same or other environments.

For example:

PROFILE_API=${API_BASE_URL}/profile

or

HEALTH_ENDPOINT=${production.BASE_URL}/health

Creating these references are error prone since they are cases sensitive and a single character mistake can lead to a broken reference.

Describe the solution you'd like

An autocomplete dropdown that shows suggestions based on the characters entered after the ${ to start a reference. For example, if creating a secret with the value:
PROFILE_API=${AP

The dropdown should match and suggest completions:

PROFILE_API=${AP...
              API_BASE_URL
              API_TOKEN

This should ideally work across environments as well, however this comes with significant complexity as secrets in other environments must be fetched and decrypted for this to work, and access to other environments will depend on the logged in user and role.

Bonus

It would also be helpful to be able to highlight referenced secrets in the editor, so the user can visually confirm that the reference is correct.

PROFILE_API=${API_BASE_URL}/profile

Hovering a reference could also show the referenced value in a tooltip

[kashyap09-01]

Hello @rohan-chaturvedi

Our team is interested in contributing to your project under FOSS Hack. Could you please assign this issue to us so we can start working on implementing a solution?

[rohan-chaturvedi]

Sure @kashyap09-01, it's all yours!

[maxgallup]

Hey!

Great work with Phase, such a delightful piece of software. What's the status on this issue? Maybe a first (easier) step would be to see whether a reference or not resolves before clicking deploy. For example if I make a typo in ${productoin.DEBUG} ideally it will warn me that there is no environment "productoin".

[nimish-ks]

Hey!

Great work with Phase, such a delightful piece of software. What's the status on this issue? Maybe a first (easier) step would be to see whether a reference or not resolves before clicking deploy. For example if I make a typo in ${productoin.DEBUG} ideally it will warn me that there is no environment "productoin".

Yes! The first step would be syntax validation.

• is secret referencing syntax correct (validate for cross env, cross app etc.)
• does a secret, environment, path, application even exist / you have permission to
• great to have: a drop down suggestion of secrets, apps, environments, paths as you are typing them. we already have a util in place that decrypts all secrets a user has access to and makes them searchable. we use this in the command palette for global secret search.

Its assigned to you.

[maxgallup]

@nimish-ks Ah unfortunately I don't have the capacity to take on such an issue at the moment. I was just wondering about whether this will still be added.