Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Plan import #1388

Merged
merged 10 commits into from
Jul 25, 2024
Merged

Feature: Plan import #1388

merged 10 commits into from
Jul 25, 2024

Conversation

duranb
Copy link
Collaborator

@duranb duranb commented Jul 18, 2024

Resolves #1154

Requires gateway PR: NASA-AMMOS/aerie-gateway#97

This feature implementation is purely functional and does not include any design considerations yet.

To test:

  1. Create a plan and add some activities, tags, and anchors
  2. Open the plan metadata and click the Export Plan icon button at the top right of the panel
  3. Verify that you've downloaded the plan JSON file
  4. Navigate to the plan creation page
  5. Click on the new Import Plan JSON File field and select the plan file that was downloaded in step 3
  6. Verify that the start/end times are pre-populated
  7. Verify that any plan tags have been populated
  8. Provide a model and unique plan name
  9. Click Create button
  10. Verify that the plan is created
  11. Verify that any anchors are correct

@duranb duranb requested a review from a team as a code owner July 18, 2024 16:43
@duranb duranb temporarily deployed to test-workflow July 18, 2024 16:43 — with GitHub Actions Inactive
@duranb duranb temporarily deployed to test-workflow July 19, 2024 19:08 — with GitHub Actions Inactive
@duranb duranb temporarily deployed to test-workflow July 19, 2024 19:13 — with GitHub Actions Inactive
@duranb duranb temporarily deployed to test-workflow July 19, 2024 22:29 — with GitHub Actions Inactive
@AaronPlave
Copy link
Contributor

This is something that could be done in a follow-up PR but could we add an e2e test that performs download, checks output against plan, upload, checks plan against old plan and json, etc?

@duranb duranb force-pushed the feature/plan-import branch from 085d5c6 to 4ec74b8 Compare July 24, 2024 14:40
@duranb duranb force-pushed the feature/plan-import branch from 4ec74b8 to 58c494b Compare July 24, 2024 16:29
@duranb duranb temporarily deployed to test-workflow July 24, 2024 16:29 — with GitHub Actions Inactive
Copy link
Collaborator

@dandelany dandelany left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 thanks @duranb - as mentioned in the gateway ticket we did some further testing of this and all looked good. Added some docs in this PR: NASA-AMMOS/aerie-docs#176

I'll go ahead and merge this for the 2.16 release.

@dandelany dandelany merged commit e86b52b into develop Jul 25, 2024
5 checks passed
@dandelany dandelany deleted the feature/plan-import branch July 25, 2024 00:01
JosephVolosin pushed a commit that referenced this pull request Aug 20, 2024
* add support for plan import

* update PlanTransfer schema to include sim args and tag colors

* export activity tags

* fix test

* derive end time from planJSON duration

* parse both DOY and YMD from plan file

* make tags optional

* import times as UTC

* sort directives by id on export

* another fix for UTC import parsing
JosephVolosin pushed a commit that referenced this pull request Oct 21, 2024
* add support for plan import

* update PlanTransfer schema to include sim args and tag colors

* export activity tags

* fix test

* derive end time from planJSON duration

* parse both DOY and YMD from plan file

* make tags optional

* import times as UTC

* sort directives by id on export

* another fix for UTC import parsing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upload and Download Plans
3 participants