harness / harness/backstage-plugins
[Feat]: Add support for migrated FME environments
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
🔖 Feature description
Paid FME customers will be migrating into app.harness.io and this code should be migrated to swap out using fme API to the harness api
🎤 Context
Right now this integration works only for un-migrated FME accounts and doesn't support what will be the post-migration world of FME directly integrated into the harness platform
✌️ Possible Implementation
I assume there is a harness api key available to use the apis? it probably should be switched to use the x-api-key header like harness normally supports and also will need to use the harness native apis to get users and groups
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
No files, tests, or entry points are named. Start by locating the existing FME API integration, then identify the Harness-native user and group APIs and their authentication requirements; done means migrated FME environments work through those APIs while existing environments remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100