fix: Enable addition of Private Repos in Spacecat via Slack and add s…

[vdua]

…… (#1372)

Please ensure your pull request adheres to the following guidelines:

• make sure to link the related issues in this description. Or if there's no issue created, make sure you
  describe here the problem you're solving.
• when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

If the PR is changing the API specification:

• make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready
  yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
• make sure you add at least one example of the request and response.

If the PR is changing the API implementation or an entity exposed through the API:

• make sure you update the API specification and the examples to reflect the changes.

If the PR is introducing a new audit type:

• make sure you update the API specification with the type, schema of the audit result and an example

Related Issues

Thanks for contributing!

[vdua]

/retest

[github-actions]

This PR will trigger a patch release when merged.

[vdua]

shall we read it from an environment variable as done here. You may need to ask in the channel to add the environment variable in the api service.

https://github.com/adobe/spacecat-import-worker/pull/442/files#diff-a4f3f338bc03c3a0a8b82bb5ed97342471ed7c5caf7e74576d342a089e472938R39

[sagarmiglani]

Thanks @vdua, I was also thinking the same. Would you also happen to if env variable AEMY_API_KEY is available to spacecat-api-worker or not?

[vdua]

I do not have access to check the env variables. Can you check in the slack channel.

[vdua]

@bosschaert Since we are invoking AEMY shall we not get all the info from there itself ? Can we add a JIRA in the backlog for the same. We would need to know the default_branch in the long term.