Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-923

Application Plan change email not sent to account email if changed via API

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • SaaS
    • System
    • 3
    • +
    • Hide

      1. Create a service with more than one Application Plan.
      2. Create a new developer account
      3. Create a new application for the developer with first Application Plan
      4. Change Application Plan from Admin Portal
      5. Observe email sent to both admin user and developer email address
      6. Change Application Plan via API

      curl -X PUT https://{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}/change_plan.xml -d "plan_id={plan_id}&provider_key={provider_key}"

      7. Observe email sent to admin but NOT to developer

      Email should be sent to both admin and developer in both cases.

      Show
      1. Create a service with more than one Application Plan. 2. Create a new developer account 3. Create a new application for the developer with first Application Plan 4. Change Application Plan from Admin Portal 5. Observe email sent to both admin user and developer email address 6. Change Application Plan via API curl -X PUT https: //{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}/change_plan.xml -d "plan_id={plan_id}&provider_key={provider_key}" 7. Observe email sent to admin but NOT to developer Email should be sent to both admin and developer in both cases.
    • 3scale 2019-03-11

      When changing an Application Plan via the API 

      /admin/api/accounts/{account_id}/applications/{id}/change_plan.xml

      An email is NOT sent to the account email. An email IS sent to admins though.

      This behavior is not exhibited when changing the Application Plan from the Admin portal. (An email IS sent to both admins and the account email in this case)

      There are some inconsistencies in notifications being sent from other API Calls.

      These two calls result in emails being sent to developers

      curl -v  -X PUT "https://{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}/suspend.xml" -d 'provider_key={provider_key}'
curl -v  -X PUT "https://{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}/resume.xml" -d 'provider_key={provider_key}'

      While these calls result in emails NOT being sent to developers

      curl -v  -X POST "https://{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}/keys.xml" -d 'provider_key={provider_key}&key=1234567890'
curl -v  -X DELETE "https://{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}/keys/1234567890.xml" -d 'provider_key={provider_key}'
curl -v  -X PUT "https://{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}/change_plan.xml" -d 'provider_key={provider_key}&plan_id={plan_id}'
curl -v  -X DELETE "https://{subdomain}-admin.3scale.net/admin/api/accounts/{account_id}/applications/{id}.xml" -d 'provider_key={provider_key}'

              Unassigned Unassigned
              rhn-support-spoole Shannon Poole
              Guilherme Cassolato Guilherme Cassolato
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: