-
Notifications
You must be signed in to change notification settings - Fork 0
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 hello.yml #77
base: main
Are you sure you want to change the base?
Create hello.yml #77
Conversation
This is a yml file that triggers GitHub actions that deploy a connector whenever code is pushed to a specific directory.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fivetran-clgritton we need some more explanation around this change, like a README file
Also a different global folder like 'example_workflow' check with @fivetran-sadiemartin
Adding this here might confuse the customers who will think its a github workflow connector.
@fivetran-sadiemartin, any thoughts on directory? /example_workflow? |
added that the file needs to be saved to .github/workflows
Very interesting question about where to put this one @varundhall and @fivetran-clgritton. I think it makes sense to create a directory for example workflows since we'll be adding terraform support in the future and probably have examples related to that. @varundhall do you think "workflow" is clear enough that we're talking about automated workflows? If so, then we could call the new directory /example_workflows |
This is a yml file that triggers GitHub actions that deploy a connector whenever code is pushed to a specific directory. It uses Environment variables and secrets to store API keys, connection names, etc.