Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create secrets.telegram_notify_bot_token so we can use it in the URL of RestApi #98

Open
chrisli30 opened this issue Jan 9, 2025 · 0 comments
Assignees
Labels
P1 Priority Level 1

Comments

@chrisli30
Copy link
Member

Although secrets all start with secrets., they have different scopes. We don’t need to implement the permission restriction for the scope now, but let’s make sure secrets have such attribute scope.

My understanding is that each secret object should contain the below properties, and we can use an array to store them [secretObj, secretObj, secretObj]

name, // the variable’s name
value, // the variable’s value
scope:

  • global // Consider calling this "app", as application-level, for example, telegram notification is just an application from our program.
  • org // Organization level, it’s a place-holder for Github organization level access
  • project // We could optionally call it workflow, but project sounds more general, and in future we might create project which can contain multiple workflows, similar to a Github repo
@chrisli30 chrisli30 added the P1 Priority Level 1 label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority Level 1
Projects
None yet
Development

No branches or pull requests

2 participants