summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2014-04-24return nil as auto_ticket_path for invalid ticketsAzul
The auto_ticket_path is referenced from the tickets_controller like this: respond_with(@ticket, :location => auto_ticket_path(@ticket)) While this only uses the location parameter when the ticket is valid it will still attampt to calculate it if not. During the create action this will lead to crashes because the ticket_path can not be calculated for a ticket without an id. This led to https://leap.se/code/issues/5552 and probably https://leap.se/code/issues/5545.
2014-04-24cert_path now is api_cert_pathAzul
2014-04-24unified wording: destroy accountAzul
2014-04-24cleanup homepage buttons someAzul
let's devide the partials rather than having super specific parameters (on_user_page)
2014-04-24add signup and login info on the formsAzul
2014-04-18Merge pull request #147 from azul/test/nagios-test-signup0.5.1-rcazul
Test/nagios test signup
2014-04-18adopt service_level config to platform settingsAzul
cost -> rate quota -> storage
2014-04-18bringing back empty cert prefixesAzul
if neither limited nor unlimited certs are allowed there will be no prefix. Not sure if this is desired - but it's the way things used to be before the refactoring
2014-04-18change service level configuration strategyAzul
The changes to the configuration required some non minor changes to the platform and also added some flexibility we don't require yet - and thus some new possibilities for errors. So instead we still use the allow_..._certs and ..._cert_prefix options. They basically provide the framework in which service levels can operate. The service level configuration will not include the cert prefix anymore. It only states if the service level is rate limited or not. This avoids conflicts between the two configuration options. I also removed the anonymous service level entirely. It was also turning a boolean decision (do we provide anonymous eip or not) into something way more complex. Instead I added the AnonymousServiceLevel class to handle the corner cases for people who are not logged in. Furthermore i renamed the UnauthenticatedUser to AnonymousUser so it matches the Anonymous Service Level nicely. It's also shorter and more intuitive.
2014-04-18minor fix: User#email_address not User#emailAzul
2014-04-17adjust test to service list in configAzul
2014-04-17make use of the UnauthorizedUserAzul
Null Pattern for current_user - use it to get rid of some conditionals
2014-04-17UnauthenticatedUser as current_userAzul
this still allows us to do current_user.service_level. Have not gone through the rest of the code yet. Only made sure logged_in? now tests for is_a? User instead of !!current_user
2014-04-17initial commit for the service level apiAzul
:api/service will return a hash of the current users service level This is failiing if the user is not logged in. Instead it should return the service description for an anonymous user.
2014-04-17add a try/except for older versions of requestsAzul
they have response.json as a dict instead of response.json()
2014-04-17nagios test: also test registering new usersAzul
2014-04-17nagios test: use support classes in soledad syncAzul
2014-04-17gitignore *.pycAzul
2014-04-17remove unneeded importsAzul
2014-04-17move support classes into their own packageAzul
now the webapp_login test looks nice and clean. soledad next.
2014-04-17nagios test: refactor webapp_login with classesAzul
2014-04-17refactor: move nagios specifs to nagios_testAzul
nagios_test.run takes a function and executes it. If it returns nothing or 0 and OK nagios message is printed. If it returns sth. else this will be printed a a warning If it raises an exception that will result in a CRITICAL report. This way we can keep the nagios things outside the test cases and just write simple functions that either return 0, a warnign or raise a meaningful exception
2014-04-17refactor reporting in webapp login nagios testAzul
2014-04-17refactor nagios tests, remove parseAzul
2014-04-17Merge pull request #146 from azul/refactor/enginesazul
Refactor/engines
2014-04-17doc: update list of enginesAzul
2014-04-11move include AssertResponses into test itselfAzul
it may not have been required before the RackTest support class.
2014-04-11minor: our engines do not have a db directoryAzul
2014-04-11move engines into engines directoryAzul
Also renamed help to support so it's harder to confuse it with documentation
2014-04-11moving broken billing integration tests out of the wayAzul
They are currently using fake_braintree. I think this is not a good approach for integration tests. It's a fake - we should test against braintrees test api. However that requires getting an api key that we want to keep outside the repository. So these test can only run on travis if we manage to setup secret values in .travis.yml - which has been failing so far. So for now i moved the broken billing integration tests to billing/test/broken to move on.
2014-04-11make sure billing tests do not interfere with othersAzul
they are still broken though.
2014-04-10bringing back srp jsAzul
2014-04-10move certs into toplevelAzul
cleaned up all the engine stuff that was never really used. Afterwards there is not that much left that makes it into the toplevel.
2014-04-08only load */test/factories from test/factoriesAzul
prevent recursive loadign of test/factories.rb ** can be empty.
2014-04-08move users: config and libAzul
2014-04-08moving users: app and test filesAzul
2014-04-08moving users: dependenciesAzul
2014-04-08update documentation: included core in toplevelAzul
now we only include some engines - we don't build the whole webapp based on them. Reflecting this in the documentation.
2014-04-08move all dependencies into GemfileAzul
We used to keep them separated so one could require some engines without using the full webapp. We've never really supported this though and probably never will.
2014-04-08fix requiring core extensions - most tests passAzul
some message tests are failing for me right now.
2014-04-08moving all of core into toplevel, tests fail.Azul
2014-04-04Merge branch 'bugfix/5382-rescue-token-destruction' into developelijah
2014-04-04redirect home when logged in visits /signup (#5446)Azul
2014-04-045382 - prevent crash when destroying tokensAzul
An expired token was removed (probably by automatic cleanup) while processing it. So the webapp crashed due to a couch 404. We're preventing that by rescueing from a 404 on Token.delete by default.
2014-04-02Merge pull request #143 from ↵varac
andrejb/bug/5430_fix-soledad_sync-returned-check_name Fix soledad sync nagios plugin returned check_name (#5430).
2014-04-02Merge pull request #142 from varac/feature/include_nagios_checksazul
Feature/include nagios checks
2014-04-02Fix soledad sync nagios plugin returned check_name (#5430).db
2014-04-02Add script to check if soledad is working (#5239).db
2014-04-02including chiiphs commentsAzul
2014-04-02autopep8 nagios webapp login testAzul