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

[17.0][WIP][MIG] connector_jira_tempo_base: Migration to 17.0 #110

Draft
wants to merge 22 commits into
base: 17.0
Choose a base branch
from

Conversation

SilvioC2C
Copy link

@SilvioC2C SilvioC2C commented Jul 10, 2024

Migration based on top of #108

@SilvioC2C SilvioC2C changed the title [17.0][WIP][MIG] connector_jira_servicedesk: Migration to 17.0 [17.0][WIP][MIG] connector_jira_tempo_base: Migration to 17.0 Jul 10, 2024
@SilvioC2C SilvioC2C force-pushed the 17.0-mig-connector_jira_tempo_base branch from 784a4a0 to 0a5093d Compare July 11, 2024 10:06
@SilvioC2C SilvioC2C force-pushed the 17.0-mig-connector_jira_tempo_base branch from 0a5093d to 548224d Compare July 11, 2024 13:48
@@ -11,8 +12,8 @@
>https://{jira-cloud-instance-name}.atlassian.net/plugins/servlet/ac/io.tempo.jira/oauth-authorize/</field>
<field name="oauth2_token_url">https://api.tempo.io/oauth/token/</field>
<field name="oauth2_flow">web_application</field>
<field name="oauth2_clientid_env_default">Fill with Server Env</field>
<field name="oauth2_client_secret_env_default">Fill with Server Env</field>
<field name="x_oauth2_clientid_env_default">Fill with Server Env</field>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why renaming oauth2_clientid_env_default to x_*?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To match the automatic name given to the field by module server_environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants