bob-skowron opened a new issue, #42262:
URL: https://github.com/apache/airflow/issues/42262
Bringing this to a top level issue. As jaklan noted below, any thoughts on
how we could manage users in MWAA given this limitation? I've also reached out
to AWS to get their thoughts.
Thanks!
Sorry for bumping the old issue, but maybe you have a quick
answer for that - AWS [added support for REST API in
MWAA](https://aws.amazon.com/blogs/big-data/introducing-amazon-mwaa-support-for-the-airflow-rest-api-and-web-server-auto-scaling/),
but the problem is - usernames in MWAA start with `assumed-role/` prefix, so
they contain slash.
Is there any way to use `/users` endpoints not to receive `The requested URL
was not found on the server. If you entered the URL manually please check your
spelling and try again.` error?
Neither `/users/assumed-role/foobar` nor `/users/assumed-role%2Ffoobar`
seems to work.
_Originally posted by @jaklan in
https://github.com/apache/airflow/issues/20063#issuecomment-2128914451_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
