naderman / composer-aws Goto Github PK

Using satis, I have created a composer repository containing one single package. This I have uploaded to an s3 bucket which is publicly accessible over http (static webpage hosting). Using this repository is working as expected.

Now I wanted to secure this repository by removing the static webpage hosting and using this composer extension. While it can read the repository meta data, composer install failed to verify the checksum of the downloaded checksum and does a fallback to the git source.

This implies, that the download process of this composer extensions seems to have some issues.

What information would be of help for resolving this issue?

I cant install

symfony/event-dispatcher suggests installing symfony/dependency-injection ()
symfony/event-dispatcher suggests installing symfony/http-kernel ()
guzzle/guzzle suggests installing guzzlehttp/guzzle (Guzzle 5 has moved to a new package name. The package you have installed, Guzzle 3, is deprecated.)
aws/aws-sdk-php suggests installing doctrine/cache (Adds support for caching of credentials and responses)
aws/aws-sdk-php suggests installing ext-apc (Allows service description opcode caching, request and response caching, and credentials caching)
aws/aws-sdk-php suggests installing monolog/monolog (Adds support for logging HTTP requests and responses)
aws/aws-sdk-php suggests installing symfony/yaml (Eases the ability to write manifests for creating jobs in AWS Import/Export)
Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.

Any idea ?

Earlier today, we tried to implements your aws plugin into our composer application, but it didn't worked.

What we tried is:

• Add it as a project's composer.json requirement (like in the README file, IMO it got no sense because it must run before to look for repositories), so it didn't worked
• Add it globally using composer global require "naderman/composer-aws:~0.2"

Every time we run a composer update we get an error saying that s3 scheme is not implemented.

We really need this feature ASAP, can you help us?

Thanks

I couldn't figure out from your documentation on how to require or setup packages.

Here is my composer.json

"installer-paths": {
            "core": ["type:drupal-core"],
            "modules/contrib/{$name}": ["type:drupal-module","type:composer-s3"],
            "profiles/contrib/{$name}": ["type:drupal-profile"],
            "themes/contrib/{$name}": ["type:drupal-theme"],
            "drush/contrib/{$name}": ["type:drupal-drush"],
            "modules/custom/{$name}": ["type:drupal-custom-module"],
            "themes/custom/{$name}": ["type:drupal-custom-theme"]
        },

{
            "type": "composer-s3",
            "url": "s3://urltofile.tar.gz" 
        }

I try to do a require

composer require bundlename.tar.gz
And get this error

 [InvalidArgumentException]
  Could not find a matching version of package bundlename.tar.gz Check the package spelling, your version constraint and that the package is available in a stability which matches your
   minimum-stability (stable).

My config.json is configured properly in composer.json and I don't get the aws key error. Help would be appreciated and updating your readme.md.

As per issue title, the plugin doesn't work with the create-project command. This seems to be a limitation of Composer in that the CreateProjectCommand class doesn't provide a preDownload hook for the plugin to insert its s3 handling into. Not sure if there is any workaround (other than to not use create-project!).

In my project, I have a local dependency on Amazon AWS SDK v3. When I installed the extension and try to run composer update I get this error:

Cannot redeclare Aws\constantly() (previously declared in /srv/laravel/vendor/aws/aws-sdk-php/src/functions.php:19)

I even tried to wrap it inside function_exists but it still did not work. It seems like the extension conflicts with already installed AWS SDK hence the error.