Download the PHP package thecatontheflat/atlassian-connect-bundle without Composer
On this page you can find all versions of the php package thecatontheflat/atlassian-connect-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download thecatontheflat/atlassian-connect-bundle
More information about thecatontheflat/atlassian-connect-bundle
Files in thecatontheflat/atlassian-connect-bundle
Package atlassian-connect-bundle
Short Description Atlassian Connect Symfony Bundle
License MIT
Homepage https://github.com/thecatontheflat/atlassian-connect-bundle
Informations about the package atlassian-connect-bundle
Atlassian Connect Bundle
About
Symfony Bundle for Atlassian Connect platform
Installation
Step 1. Add bundle to composer dependencies
Step 2. Enable the bundle
Add the bundle to config/bundles.php
Step 3. Bundle configuration
The bundle descriptor is used to install your app on Atlassian. When requesting descriptor - this configuration is converted to JSON.
Sample configuration in packages/atlassian-connect.yaml
:
If you need to overwrite any config in dev/test environment, overwrite that config in the packages/{env}/atlassian-connect.yaml
file.
Step 4. Security configuration
To configure security part - use the following configuration in your security.yml
. If you have another firewall that has the "^/"
pattern, be sure to set the jwt_secured_area
firewall first.
Step 5. Include Routes
Add the following configuration to config/routes.yaml
:
Step 6. (Optional): Configure License Check
To perform a license check for a certain route - specify the requires_license
default in your routing.yml
Step 7. Update Database
Usage Examples
Signed Request
In your protected controller action you can make a signed request to JIRA instance:
Whitelisting licences
You could whitelist any licence by editing related row in table tenant and setting field is_white_listed to 1. If you will also set white_listed_until - you will be able to set whitelist expiration
Dev environment
In dev environment Tenant with id=1 would be used automatically. You could set configuration variable atlassian_connect.dev_tenant to false in order to disable it, or use another dev tenant id. It would allow you to test your plugin output for any tenant.
Custom tenant entity
If you need to add more properties to tenant entity or reverse-side of your app entity relations - you could override default Tenant entity like
And override default one by setting parameter
In order to use it you will need to disable doctrine automapping
Troubleshooting
Cant start free trial of my plugin on Jira Cloud
As soon as you will create your plugin - you will be able to access plugin manifest via url https://yourplugindomain.com/atlassian-connect.json
You will be able to setup it in "Manage Addons" section of your Jira Cloud using "Upload addon" interface. But right now AtlassianConnectBundle support only "paid via Atlassian" model, so you will not be able to start your trial.
Instead of using manifest url directly - you should add private listing of your plugin, create token and get manifest url like
https://marketplace.atlassian.com/files/1.0.0-AC/artifact/descriptor/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/atlassian-connect.json?access-token=xxxxxxxx
If you will use that url from marketplace - your trial will be started automatically.
All versions of atlassian-connect-bundle with dependencies
ext-json Version *
symfony/dependency-injection Version ^5.4|^6.3|^7.0
symfony/http-kernel Version ^5.4|^6.3|^7.0
symfony/config Version ^5.4|^6.3|^7.0
symfony/http-client Version ^5.4|^6.3|^7.0
symfony/yaml Version ^5.4|^6.3|^7.0
symfony/security-bundle Version ^5.4|^6.3|^7.0
symfony/routing Version ^5.4|^6.3|^7.0
symfony/console Version ^5.4|^6.3|^7.0
doctrine/orm Version ^2.5
twig/twig Version ^2.10|^3.0
firebase/php-jwt Version ^6.2