Github actions reusable workflow secrets inheritance not working

[guillermomolla]

Select Topic Area

Bug

Body

I am working on creating a system with Github actions for some tasks with docker and I am having some issues with it.
I have 2 files in 2 diferent repos:

workflow.yml:

on: workflow_call
env:
  AWS_ACCESS_KEY_ID: {{ secrets.AWS_ACCESS_KEY_ID }}
  AWS_SECRET_ACCESS_KEY: {{ secrets.AWS_SECRET_ACCESS_KEY }}
  AWS_REGION: {{ secrets.AWS_DEFAULT_REGION }}
  AWS_DEFAULT_REGION: {{ secrets.AWS_DEFAULT_REGION }}
  REGISTRY: {{ secrets.DOCKER_REGISTRY }} #url of docker registry on ecr
jobs:
  build:
    runs-on: self-hosted
    steps:
      - name: ECR credentials
        run: aws ecr get-login-password | docker login -u AWS "$REGISTRY" --password-stdin $REGISTRY

callworflow.yml:

on: workflow_dispatch
jobs:
  test:
    uses: organization/example-repo/.github/workflows/workflow.yml@main
    secrets: inherit

On trying to launch the reusable workflow from actions I get an error:

Error: Cannot perform an interactive login from a non TTY device

In my organization I have all secrets. Even doing the process directly on a workflow instead of using the reusable workflow call works.
So I am misunderstanding something or what is happening? The documentations says something like:

If the secrets are inherited by using secrets: inherit in the calling workflow, you can reference them even if they are not explicitly defined in the on key. 

I also tried to add the envs to the callworkflow.yml file or even calling directly {{ secrets.DOCKER_REGISTRY }} on the workflow.yml instead of using an env.

Thank you for you help in advance

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐