feat: provisioning api skeleton

[iloveagent57]

https://2u-internal.atlassian.net/browse/ENT-9970

1. Ensure your requesting user is either a superuser or has the enterprise_provisioning_admin role assigned via edxapp: http://localhost:18000/admin/enterprise/systemwideenterpriseuserroleassignment/add/
2. Make POST request to http://localhost:18270/api/v1/provisioning with body like

{
    "enterprise_customer": {
        "name": "Test customer",
        "country": "US",
        "slug": "test-customer"
    },
    "pending_admins": [
        {
            "user_email": "[email protected]"
        }
    ]
}

3. Observe ack response.

Merge checklist:

• ./manage.py makemigrations has been run
  • Note: This must be run if you modified any models.
    • It may or may not make a migration depending on exactly what you modified, but it should still be run.

Post merge:

• Ensure that your changes went out to the stage instance
• Deploy to prod instance

[openedx-webhooks]

Thanks for the pull request, @iloveagent57!

This repository is currently maintained by @openedx/2u-enterprise.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[adamstankiewicz]

LGTM, with a nit/question!

[adamstankiewicz]

[nit/curious] Once a customer has been provisioned, presumably a slug will always exist at this point? Even if no slug is provided in the request, I believe the intent is to generate a slug? If so, should slug be a required field in the response?

[iloveagent57]

That's a good point, slug should be required in the response. Your question raises another good point in my mind - I should document in an ADR the intended set of provisioning endpoints, which will actually inform how we should be designing these serializers.

1. The create() view should idempotently get-or-create, but not modify, customers and their associated records. This endpoint is the primary goal for MVP purposes.
2. There should be a modify view that's a get-or-update type of operation.

[pwnage101]

The entire concept of adding a new system-wide role is new to me. Don't we have to create this on the edxapp side now? Why not just assign PROVISIONING_ADMIN_ROLE to SYSTEM_ENTERPRISE_OPERATOR_ROLE so that only backend services and operational staff can call this endpoint?

[iloveagent57]

Good question - this role already exists (which surprised me). I'm not quite sure of the motivation for it, but it's there so I used it. But maybe we should additionally assign the provisioning feature role to the system operator role.

[adamstankiewicz]

But maybe we should additionally assign the provisioning feature role to the system operator role.

Agreed! ➕ 1️⃣