Sackmesser - Developer Email Address - Casing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 221
- Forks
- 174
- PR merge metrics
- No merged PRs in 30d
Description
The sackmesser tool is capable of performing edge exports that can be used to import into Apigee X. When using the exported content, one error that we ran into when executing and import was POST https://apigee.googleapis.com/v1/organizations//developers
{
"error": {
"code": 400,
"message": "email address has to be lowercase",
"status": "INVALID_ARGUMENT"
}
}
Would it make sense to either add a flag for the type of env it's planned to be imported to or similar, in order to trigger a thing (sed, etc..) to clean this up?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the sackmesser edge-export path and how developer email addresses are emitted for Apigee X imports. Determine the appropriate handling for mixed-case addresses, such as normalization or an import-target option. Done means exported content no longer fails Apigee X with the lowercase email-address error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100