Add secrets

[v9n]

Fix #98

[chrisli30]

Is the scope mentioned in the #98 implemented in this PR? It needs to be set when a secret is created.

Also, what is the call of adding a secret?

[v9n]

Is the scope mentioned in the #98 implemented in this PR? It needs to be set when a secret is created.

Also, what is the call of adding a secret?

haven’t implemented the scope or the functionality for adding secrets in this PR yet. The main reason is that I’m not entirely sure how we’d like to handle secret management moving forward, so I’ve deferred implementing that until we have a clearer direction.

For now, the code is designed to allow the use of global secrets that are pre-defined in the configuration. It looks something like this, and additional secrets can be added there as needed:

Could you clarify your vision for how you’d like secret management and the addition/removal of secrets to work? I’d also like to understand more about how you see the scope parameter being used in this context.

I do have my own ideas on this, but right out they already conflicted with the current definition of scope and the approach of using an array to store the secrets (e.g., [secretObj, secretObj, secretObj]). I’d prefer to start with your perspective so we can align and refine the implementation together.

[v9n]

@chrisli30 As dicussed on the chat, this is global secret. Define statically in the config file. Manage by AP. There is no way to dynamically add the global secret through API.

The secret will all have AP_ prefix.

Then we will create another issue to document on how an end-user will create and manage the secret to be used in their project.