Bug report: Console cannot edit Glue triggers with certain characters in name

Thank you for reporting this issue with AWS Glue triggers. You've identified an important inconsistency in the AWS Glue console's handling of special characters in trigger names.

The problem you're experiencing is indeed a bug in the AWS Glue console. The console is allowing the creation of triggers with special characters like forward slashes (/) and question marks (?) in their names, but it's not properly handling these characters when attempting to edit the triggers later.

This behavior is unexpected and not in line with AWS Glue's intended functionality. Typically, AWS services have restrictions on special characters in resource names to avoid issues with URL encoding and API calls. The fact that you can create triggers with these characters but can't edit them indicates a discrepancy between the creation and editing processes in the console.

For the forward slash (/), the 404 error suggests that the console is interpreting the character as part of the URL path, leading to an invalid URL when trying to access the edit page.

For the question mark (?), the "Trigger not found" error implies that the character is interfering with the API call to fetch the trigger details, possibly due to it being interpreted as a query string separator in the URL.

As a workaround, you may be able to edit these triggers using the AWS CLI or AWS Glue API instead of the console. However, this is not an ideal solution.

Your suggestion for expected behavior is correct. AWS should either:

1. Allow the use of these special characters consistently throughout the trigger lifecycle (creation, editing, deletion), ensuring proper handling in the console and API calls, or
2. Prevent the use of these special characters in trigger names from the outset, providing clear validation during the trigger creation process.

I recommend reporting this issue to AWS Support so they can address it in a future update to the AWS Glue console. In the meantime, it's best to avoid using special characters like slashes and question marks in your AWS Glue trigger names to prevent such issues.
Sources
Triggers - AWS Glue
AWS Glue triggers - AWS Glue

Hi

I can see that you are not able to use the console to edit a Glue trigger which contains certain characters in the name. The console allows to create a trigger with special characters in the name, but once created, the trigger can't be edited with the console.

I have replicated the same and even I am getting the same error while using A/B or A?B as the name of the glue trigger. It seems URL encoding is not happening when we edit the trigger like it does when we click on trigger, this is indeed a bug in the AWS Glue console. Hence, I will report this issue internally and request Service team to get it fixed.

However, as a workaround to edit the trigger with certain characters in name you can follow the below steps :

1. When you click on the trigger name (A/B or A?B), copy the last part of the URL, which is the encoded trigger name (e.g., "a%252Fb"). Please see the below URL for the reference. https://region.console.aws.amazon.com/glue/home?region=your-region#/v2/etl-configuration/triggers/view/a%252Fb

2. Then, click on the "Edit trigger" option, and in the URL, replace the last part (e.g., "a/b") with the encoded trigger name you copied in step 1 (e.g., "a%252Fb"). Please see the below URL for the reference. https://region.console.aws.amazon.com/glue/home?region=your-region#/v2/etl-configuration/triggers/edit/a/b

I hope the above information helps.

Thank you !